Method and System for Performing Affinity Transactions

ABSTRACT

There is provided a physical token for use in a defined venue with a server having communication with the physical token. The physical token may comprise an identification data and a transmitter configured to transmit the identification data. The physical token is configured to transmit the identification data to the server to cause the server to initiate a sensory interaction with a user possessing the physical token. The sensory interaction may comprise a character in the defined venue interacting with the user possessing the physical token. The sensory interaction may also comprise a display screen in the defined venue displaying information to the user possessing the physical token. The sensory interaction may further comprise an audio speaker in the defined venue announcing information to the user possessing the physical token. The physical token may represent an affinity comprising an experience, entitlement, or characteristic of the user possessing the physical token.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is generally in the field of communication. Moreparticularly, the present invention relates to identification andassociation in communication systems.

2. Background Art

Defined venues rely upon a limited set of conventional means fortracking guest affinities and performing affinity transactions such as,for example, affinities for particular venue attractions, venuecharacters, or venue features. Such conventional means include, forexample, a paper ticket and a plastic wristband. A paper ticket, forexample, may be typically issued to a guest of a movie theater definedvenue with the expectation that the guest will maintain possession ofthe paper ticket for the duration of a movie showing. Similarly, aplastic wristband, for example, may be typically issued to a guest of amusic concert defined venue with the expectation that the guest willwear the plastic wristband while at the concert. Based on the guest'spossession and display of the paper ticket or plastic wristband, thevenue can infer particular affinities of the guest, and may performappropriate affinity transactions. For example, the color or shape ofthe paper ticket or plastic wristband might indicate a particular guestaffinity.

These various conventional means for tracking guest affinities haveassorted drawbacks. For example, both paper tickets and plasticwristbands, if easily transferable, can pass from guest to guest forre-use, often against the policy of a defined venue. Additionally, aguest must maintain possession of a paper ticket or a plastic wristbandand keep it readily displayed so that the venue can easily track theaffinity represented. Furthermore, if in some circumstances a guestpossesses a variety of paper tickets or wristbands at once it may bedifficult or impossible for the venue to precisely reconcile the variousrepresented affinities and to respond with an appropriate affinitytransaction.

Accordingly, there is a need to overcome the drawbacks and deficienciesin the art by offering an improved method and system for tracking guestaffinities and performing affinity transactions.

SUMMARY OF THE INVENTION

There are provided methods and systems for performing affinitytransactions, substantially as shown in and/or described in connectionwith at least one of the figures, and as set forth more completely inthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present invention will become morereadily apparent to those ordinarily skilled in the art after reviewingthe following detailed description and accompanying drawings, wherein:

FIG. 1 shows a diagram of an exemplary system for performing affinitytransactions, according to one embodiment of the present invention;

FIG. 2 shows a flowchart presenting an exemplary method for performingaffinity transactions, according to one embodiment of the presentinvention; and

FIG. 3 shows a diagram of an exemplary identification band with securedassociation to the wearer including physical tokens for performingaffinity transactions, according to one embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is directed to a method and system for performingaffinity transactions. Although the invention is described with respectto specific embodiments, the principles of the invention, as defined bythe claims appended herein, can obviously be applied beyond the specificembodiments of the invention described herein. Moreover, in thedescription of the present invention, certain details have been left outin order to not obscure the inventive aspects of the invention. Thedetails left out are within the knowledge of a person of ordinary skillin the art. The drawings in the present application and theiraccompanying detailed description are directed to merely exemplaryembodiments of the invention. To maintain brevity, other embodiments ofthe invention, which use the principles of the present invention are notspecifically described in the present application and are notspecifically illustrated by the present drawings.

FIG. 1 shows exemplary system 100 according to one embodiment of thepresent invention. System 100 may be utilized, for example, to performvarious affinity transactions in a defined venue, such as a theme park(e.g. Disneyland). System 100 comprises user 102, physical token 104 a,and physical token 104 b. Physical tokens 104 a and 104 b are, in oneembodiment, worn on the person of user 102 or in possession of user 102,and are configured to engage in transmission 130 a and transmission 130b during an affinity transaction by utilizing a transmitter. System 100also comprises venue transceiver 110, venue server 112, and venueoperator 118. Venue operator 118 is utilized by venue server 112 tocomplete an affinity transaction by performing sensory interaction 136.Network 120, in one embodiment a computer network as known in the art,is utilized for communication between venue transceiver 110, venueserver 112, and venue operator 118 of system 100.

Physical token 104 a, which in one embodiment represents an affinity ofuser 102, comprises a transmitter and an identification data accordingto the present invention. In one embodiment, the transmitter isimplemented as an RFID device configured to store the identificationdata as a unique serial number, and also configured to transmit theunique serial number. Physical token 104 a is configured to transmit theidentification data to venue server 112 via network 120 and venuetransceiver 110, which in one embodiment is implemented as an RFIDtransceiver. Physical token 104 a may be associated with physical token104 b or with virtual token 105 c, as described further below.

Physical token 104 a is designed in one embodiment as a pin to be pinnedto the clothing of user 102, while in another embodiment physical token104 a may be designed as a necklace or another item of adornment thatcan be worn, while in yet another embodiment physical token 104 a is atoken or chip that can be carried by user 102. In one embodiment shownin FIG. 3, physical token 104 a can correspond to physical token 312 orphysical token 314, attached to wristband 301 with a loop or cord, orcan correspond to physical token 310, attached to wristband 301 with anadhesive. In another embodiment, physical token 104 a correspondsdirectly to wristband 301, comprising transmitter 302 coupled to memory304 configured to store the identification data. In one embodiment,physical token 104 a comprises (or is configured to be coupled to adevice comprising) security and identification features as described inU.S. patent application Ser. No. [TBD] titled “Identification Band withSecured Association to the Wearer,” Attorney Docket No. 0260170, andassigned to Disney Enterprises, Inc., which is hereby incorporated byreference in its entirety. Physical token 104 b is configured in amanner similar to physical token 104 a.

In one embodiment, physical token 104 a represents an affinity stored asaffinity record 105 a in affinity database 116 of venue server 112.Affinity database 116 is, for example, a database stored on a hard driveand executing on a processor of venue server 112, as known in the art.Affinity database 116 comprises affinity record 105 a and other affinityrecords. For example, affinity database 116 also comprises affinityrecord 105 b, which in one embodiment is an affinity represented byphysical token 104 b, and comprises affinity record 105 c, which in oneembodiment is an affinity not represented by a physical token (i.e., isa virtual token). An affinity stored as an affinity record may be, forexample, an experience had by user 102 (e.g., user 102 went on theIndiana Jones Adventure ride at Disneyland), an entitlement or purchasemade by user 102 (e.g., user 102 bought a Mickey Mouse hat), anaccomplishment or reward of user 102 (e.g., user 102 completed a MagicKingdom video game), or a characteristic that user 102 identifies with(e.g., user 102 is a fan of the movie character Jack Sparrow).

System 100, in one embodiment, comprises a plurality of physical tokensand a plurality of virtual tokens, and user 102 can acquire physicaltokens, such as physical tokens 104 a and 104 b, in a variety of ways atvarious first points of interest. For example, user 102 may receivephysical token 104 a from a ticket clerk when purchasing admission toDisneyland. As such, physical token 104 a may represent, by affinityrecord 105 a, that user 102 purchased admission to the theme park, forexample, on a particular date. For another example, user 102 may enterthe theme park and later receive physical token 104 b from a mechanicaldispenser inside Disneyland while waiting in line for the Mark TwainRiverboat ride. As such, physical token 104 b, distributed to user 102in line for the ride, may represent, by affinity record 105 b, that user102 went on the ride.

After acquiring one or more physical tokens, user 102 may utilize thephysical token or tokens to perform affinity transactions at varioussecond points of interest. User 102 may do so by utilizing physicaltokens alone or in combination. For example, user 102 may use physicaltoken 104 a alone, or in combination with physical token 104 b. Asstated above, in one embodiment physical token 104 a may represent, byaffinity record 105 a, that user 102 purchased admission to Disneylandon a particular date. Thus, user 102 may utilize physical token 104 aalone to perform an affinity transaction to retrieve that information.In particular, user 102 may place physical token 104 a in closeproximity to venue transceiver 110, configured in this example as ashort-range RFID reader, such that venue transceiver 110 reads the RFIDdevice of physical token 104 a, and sends the unique serial number ofphysical token 104 a to venue server 112 via network 120. Venue server112 may retrieve affinity record 105 a in affinity database 116,retrieve the date (i.e., the affinity represented by physical token 104a) and transmit the date to venue operator 118, which in this example isconfigured as a display screen coupled to venue transceiver 110. User102 may thus, during sensory interaction 136, read the date displayed onthe display screen on which physical token 104 a was purchased.

User 102 may utilize physical tokens in combination to perform affinitytransactions with the assistance of association database 114 of venueserver 112. Like affinity database 116, association database 114 is, forexample, a database stored on a hard drive and executing on a processorof venue server 112, as known in the art. Association database 114comprises, in one embodiment, association record 107, association record108, and other association records not shown. Association record 107represents an association of physical tokens 104 a and 104 b, andassociation record 108 represents an association of physical token 104 aand virtual token 105 c. An association, so represented, may indicatethat a user, e.g. user 102, has more than one physical token in hispossession, for example, or has associated a physical token with avirtual token.

As stated above, in one embodiment physical token 104 a may represent,by affinity record 105 a, that user 102 purchased admission Disneylandon a particular date. Additionally, physical token 104 b may represent,by affinity record 105 b, that user 102 went on the Mark Twain Riverboatride in the theme park. Thus, user 102 may use physical token 104 a incombination with physical token 104 b to perform an affinity transactionto retrieve that information in combination. In particular, user 102 mayput physical token 104 a and physical token 104 b in close proximity tovenue transceiver 110, configured as a short-range RFID reader, suchthat venue transceiver 110 reads the RFID device of both physical tokens104 a and 104 b, and sends the unique serial numbers to venue server 112via network 120.

Venue server 112 is configured, in one embodiment, to recognize thesimultaneity of transmissions 130 a and 130 b and thereby createassociation record 107 in step 132. Association record 107 associatesphysical tokens 104 a and 104 b in association database 114, and may beutilized to complete an affinity transaction initiated by user 102. Forexample, after step 132, venue server 112 may transmit the purchase dateand ride information stored in affinity records 105 a and 105 b to venueoperator 118, configured as a display screen coupled to venuetransceiver 110. User 102 may thus read the date physical token 104 awas purchased and the information about the Mark Twain Riverboat ride onvenue operator 118 during sensory interaction 136. In anotherembodiment, venue operator 118 may be configured as a Mark Twaincharacter who interacts with user 102 during sensory interaction 136.Notably, because the affinities of affinity records 105 a and 105 b areassociated in association record 107, subsequent affinity transactionscan invoke or utilize all such associated affinities by utilizing onlyphysical token 104 a or only physical token 104 b.

For example, after association record 107 has been created inassociation database 114, user 102 may utilize a single physical token,e.g. physical token 104 a, to perform an affinity transaction in thetheme park that involves affinities of affinity records 105 a and 105 b.For example, in an embodiment where physical token 104 a may be read byvenue transceiver 110 implemented as a long-range RFID reader, butphysical token 104 b can only be read by a short-range RFID reader, anaffinity transaction involving the affinities that both physical tokens104 a and 104 b represent can be performed by reading only physicaltoken 104 a and then looking up association record 107. In particular,user 102 may put physical token 104 a in sufficient proximity to venuetransceiver 110, configured as a long-range RFID reader, such that venuetransceiver 110 reads the RFID device of physical token 104 a and sendsthe unique serial number of physical token 104 a to venue server 112 vianetwork 120. Venue server 112 may then retrieve association record 107and affinity records 105 a and 105 b in affinity database 116, retrievethe date and ride information (i.e., the affinities represented byphysical tokens 104 a and 104 b) and transmit the date and rideinformation to venue operator 118, which may complete the affinitytransaction during sensory interaction 136 in a manner described above.

Thus, as discussed above, in various embodiments physical token 104 amay be utilized alone to perform an affinity transaction, or may beutilized in combination with physical token 104 b. In addition, physicaltoken 104 a may be utilized to perform an affinity transaction withvirtual token 105 c. For example, user 102 may utilize physical token104 a to perform an affinity transaction in the theme park while playinga Magic Kingdom video game, and virtual token 105 c may represent avideo game accomplishment. While user 102 is playing the video game,which in one embodiment comprises venue transceiver 110 implemented asan RFID transceiver, user 102 may stand close enough to the video gamesuch that venue transceiver 110 reads the RFID device of physical token104 a and sends the unique serial number of physical token 104 a tovenue server 112 via network 120. Venue server 112 is configured, in oneembodiment, to recognize the proximity of user 102 to the video game andthereby create association record 108 in step 134, thereby associatingphysical token 104 a and virtual token 105 c in association database114.

After step 134, user 102 may utilize a single physical token, e.g.physical token 104 a, to perform an affinity transaction in the themepark that involves affinities of affinity records 105 a and 105 c. Forexample, after being provided physical token 104 a at a first point ofinterest (e.g. from a ticket clerk at the entrance of Disneyland), andafter playing the Magic Kingdom video game, user 102 may leave thearcade where the video game is located and review the video game from asecond point of interest, such as a Disney-themed cafe near the arcade.An instance of venue transceiver 110 implemented as a RFID reader maydetect the presence of physical token 104 a at the second point ofinterest, and user 102 may put physical token 104 a in sufficientproximity to venue transceiver 110 such that venue transceiver 110 readsthe RFID device of physical token 104 a and sends the unique serialnumber of physical token 104 a to venue server 112 via network 120.Venue server 112 thereby receives the identification data of physicaltoken 104 a and retrieves an affinity represented by physical token 104a (e.g. retrieves association record 108 and affinity records 105 a and105 c). Venue server 112 may then initiate a sensory interaction withuser 102 possessing physical token 104 a by, for example, configuringvenue operator 118 as an audio speaker that announces video game scores,thereby completing the affinity transaction during sensory interaction136.

In one embodiment, user 102 may utilize physical token 104 a to performan affinity transaction outside the theme park after leaving the themepark. After being provided physical token 104 a at a first point ofinterest (e.g. after being photographed at a picture station inDisneyland), user 102 may leave the theme park and review pictures takenat the picture station from, for example, a home computer (e.g., asecond point of interest). In one embodiment, the home computer of user102 includes venue transceiver 110 implemented as an RFID reader coupledto the home computer via, for example, a USB cable. In anotherembodiment, user 102 enters the unique serial number of physical token104 a into a keyboard or other input device of the home computer. Thehome computer, in one embodiment coupled to network 120 via theInternet, then sends the unique serial number of physical token 104 a tovenue server 112. Venue server 112 thereby receives the identificationdata of physical token 104 a and retrieves an affinity represented byphysical token 104 a (e.g. retrieves an affinity record comprising thepictures taken at the picture station). Venue server 112 may theninitiate a sensory interaction with user 102 by, for example,configuring the home computer of user 102 as venue operator 118 todisplay the pictures. For example, the home computer may display thepictures via a personalized web page or virtual scrapbook, therebycompleting the affinity transaction during sensory interaction 136.

FIG. 2 shows flowchart 200 of an exemplary method for performingaffinity transactions, according to one embodiment of the presentinvention. Certain details and features have been left out of flowchart200 that are apparent to a person of ordinary skill in the art. Forexample, a step may comprise one or more substeps or may involvespecialized equipment or materials, as known in the art. While steps 210through 226 indicated in flowchart 200 are sufficient to describe oneembodiment of the present invention, other embodiments of the inventionmay utilize steps different from those shown in flowchart 200.

In step 210 of flowchart 200, a physical token, for example physicaltoken 104 a in FIG. 1, is received by a user, such as user 102. Thephysical token comprises a transmitter and an identification data, whichmay be implemented in one embodiment as an RFID device configured totransmit a unique serial number. The physical token may be utilized toperform various affinity transactions in a defined venue, such asDisneyland. The user may receive the physical token a variety of ways.For example, the user may receive the physical token from a ticket clerkwhen purchasing admission to the theme park, or later from a mechanicaldispenser inside the theme park while waiting in line for a ride.

In step 212 of flowchart 200, the physical token transmits theidentification data to a server in the venue. The server, whichcorresponds in one embodiment to venue server 112 in FIG. 1, receivesthe identification data via a venue transceiver corresponding to venuetransceiver 110, and via a network corresponding to network 120. Theserver comprises, for example, an affinity database corresponding toaffinity database 116 and an association database corresponding toassociation database 114. Both the affinity and the association databasemay be stored on a hard drive and may execute on a processor of theserver, as known in the art.

In step 214 of flowchart 200, the server retrieves an affinityrepresented by the physical token. In particular, in one embodiment theserver retrieves the affinity from the affinity database by, forexample, searching the database for an affinity record matching theidentification data transmitted from the physical token. The affinitymay comprise, for example, an experience, an entitlement, anaccomplishment, or a characteristic of the user of the physical token.

In step 216 of flowchart 200, the server determines whether to associatethe physical token to a second physical token or to a virtual token. Asecond physical token corresponds, in one embodiment, to physical token104 b of FIG. 1, while a virtual token corresponds, in one embodiment,to affinity record 105 c. The server may make such a determination basedon several factors. For example, in one embodiment the server isconfigured to recognize the simultaneity of transmission ofidentification data from both physical tokens. In another embodiment,for example, the server is configured to recognize the proximity of thephysical tokens to one another. The user may have received the secondphysical token from, for example, a mechanical dispenser insideDisneyland while waiting in line for a ride. As such, the secondphysical token may represent that the user went on the ride. The servermay associate the physical tokens by, for example, creating anassociation record corresponding to association record 107 in theassociation database during step 218. In a second example, the server isconfigured to recognize that the user is playing a video game when theidentification data is transmitted from the physical token. In such acircumstance the server may associate the physical token and a virtualtoken representing a video game accomplishment by, for example, creatingan association record corresponding to association record 108 duringstep 218.

Some affinity transactions may terminate after performing step 218, ifduring step 220 the server determines that no further action needs to betaken. For example, flowchart 200 may terminate and return to step 212if, for example, in step 218 a virtual token representing a video gameaccomplishment was associated to the physical token, and the user hasstopped playing the video game. In another example, flowchart 200 mayinstead proceed to step 222 via step 220 if during step 218 a secondphysical token was associated to the physical token and the serverdetermines that, for example, a sensory interaction corresponding tosensory interaction 136 should be performed via a venue operatorcorresponding to venue operator 118 in FIG. 1.

In step 222 of flowchart 200, the server determines whether a secondphysical token or virtual token is associated with the physical token.If a token is not so associated, then the server proceeds to perform anaffinity transaction utilizing only the affinity represented by thephysical token by, for example, performing an interaction with the venueoperator in step 226. In contrast, if a token is so associated, then instep 224 the server may proceed to perform an affinity transactionutilizing the affinity represented by the physical token as well as theaffinity represented by the associated physical or virtual token withthe venue operator. After completing the affinity transaction in eitherstep 226 or 224, flowchart 200 returns to step 212, whereby the user mayinitiate another affinity transaction.

In the manner described above, the invention as shown in exemplarysystem 100 and exemplary flowchart 200 achieves improved tracking ofguest affinities and performing of affinity transactions whileovercoming the drawbacks of conventional solutions. Physical and virtualtokens utilized by the invention may, for example, be received by auser, associated, and utilized in affinity transactions via systems ormethods as described above. The drawbacks of conventional solutions,which are, for example, less precise, are avoided.

From the above description of the invention it is manifest that varioustechniques can be used for implementing the concepts of the presentinvention without departing from its scope. Moreover, while theinvention has been described with specific reference to certainembodiments, a person of ordinary skill in the art would recognize thatchanges can be made in form and detail without departing from the spiritand the scope of the invention. The described embodiments are to beconsidered in all respects as illustrative and not restrictive. Itshould also be understood that the invention is not limited to theparticular embodiments described herein, but is capable of manyrearrangements, modifications, and substitutions without departing fromthe scope of the invention.

1-20. (canceled)
 21. A system for use in a defined venue, the systemcomprising: a server having a database; a first physical token includinga first identification data identifying a user possessing the firstphysical token; a second physical token including a secondidentification data identifying an experience of the user gained in thedefined venue; wherein the server is configured to: receive the firstidentification data from the first physical token possessed by the user;receive the second identification data from the second physical tokenpossessed by the user; and associate the first physical token and thesecond physical token in the database.
 22. The system of claim 21,wherein the server is configured to initiate a sensory interaction withthe user, the sensory interaction comprising a movie character in thedefined venue interacting with the user.
 23. The system of claim 21,wherein the server is configured to initiate a sensory interaction withthe user, the sensory interaction comprising a display screen in thedefined venue displaying information to the user.
 24. The system ofclaim 21, wherein the server is configured to initiate a sensoryinteraction with the user, the sensory interaction comprising an audiospeaker in the defined venue announcing information to the user.
 25. Thesystem of claim 21, wherein the server is configured to initiate asensory interaction with the user, and wherein the server is furtherconfigured to perform the sensory interaction utilizing a venueoperator.
 26. The system of claim 21, wherein the first identificationdata comprises a unique serial number.
 27. A method for use by a serverhaving a database for a defined venue, the method comprising: receivinga first identification data from a first physical token possessed by auser, the first physical token including a first identification dataidentifying the user; receiving a second identification data from asecond physical token possessed by the user, the second physical tokenincluding a second identification data identifying an experience of theuser gained in the defined venue; and associating the first physicaltoken and the second physical token in the database.
 28. The method ofclaim 27 further comprising: initiating a sensory interaction with theuser, the sensory interaction comprising a movie character in thedefined venue interacting with the user.
 29. The method of claim 27further comprising: initiating a sensory interaction with the user, thesensory interaction comprising a display screen in the defined venuedisplaying information to the user.
 30. The method of claim 27 furthercomprising: initiating a sensory interaction with the user, the sensoryinteraction comprising an audio speaker in the defined venue announcinginformation to the user.
 31. The method of claim 27 further comprising:initiating a sensory interaction with the user, and wherein the serveris further configured to perform the sensory interaction utilizing avenue operator.
 32. The method of claim 27, wherein the firstidentification data comprises a unique serial number.